Skip to main content

2024-05 Release Notes

Iteration: 2024-05

May 3rd, 2024

Whats New?

6185Friendlier usernames for customers!

Improvements

6132Removed county data from [ENROLL_SERVICE_ADDRESS] and [ENROLL_BILLING_ADDRESS] dynamic fields.
\(＾▽＾)/It’s possible to edit Date of Birth on the Enrollment Details page.
\(＾▽＾)/It’s possible to change an existing ESG token on the Enrollment Details page.
\(＾▽＾)/Added Meter Number to Web/Quick Enrollments Summary Page.
\(＾▽＾)/Added validations to the Sales Importer to warn users about bad formatting on dates or extra empty rows at the end of the file.
\(＾▽＾)/Better logs on Market Manager, Commodity Types, Utility Manager.
\(＾▽＾)/Performance improvements on recurring billing management.
\(＾▽＾)/Added an “Archived” field to Autoresponder packages.

Fixes 

6173Fix for issue where recurring billing status for renewals was not being inherited from original enrollment.
6239Adjusted validation on Beta Sales Importer so accounts are linked to the correct plan.
¯\_(ツ)_/¯Several adjustments on the task that syncs dates with P2C to prevent performance issues.
¯\_(ツ)_/¯Corrected issue with the calendar components across the whole system that would not refresh despite having clicked on the “Clear” button.
¯\_(ツ)_/¯Numerous fixes on Background Service related to logging the service activity and issues.
¯\_(ツ)_/¯Enrollments API: Resolved zip code parameter issue on Utilities endpoint.
¯\_(ツ)_/¯Resolved issues on Background Service tasks related to meter numbers.

Features & Fixes Details

Friendlier usernames for customers​

To avoid duplicate usernames, OpsAdmin would create usernames with random letters or numbers that would end up being very confusing for customers and hard to remember. To improve the process of logging in to the MyAccount site, the mechanism to create usernames has been revamped.

Now, the system attempts to create the username using the customer’s first part of the email address. If that is already an existing username, the system will attempt to use the full email address. If that option is taken, the next option is using first + last name. If that is in use, last + first, then L + first; FirstLast; LastFirst, phone, and lastly FirstName+ [Random Number]. If the customer is a Business, it will also attempt to use the firm name.

So, to summarize: The system will try as much as possible to create a username that’s friendly to the customer. If all the possibilities are existing usernames in  the database, a random string will be generated.

Added an “Archived” field to Autoresponder packages​

Now it’s possible to archive autoresponder packages. This serves two purposes:

  • A new organization tool to hide autoresponders no longer used.

  • Hiding autoresponders that use triggers that are no longer available, but keeping the history at the same time.

The filters in the Autoresponder Packages screen and the Autoresponders screen are configured to hide the archived items by default, being an option to show only the archived or everything.